Skip to content

Conversation

@BoxyUwU
Copy link
Member

@BoxyUwU BoxyUwU commented Dec 5, 2025

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels Dec 5, 2025
@BoxyUwU
Copy link
Member Author

BoxyUwU commented Dec 5, 2025

@bors r+ rollup=never p=10

@bors
Copy link
Collaborator

bors commented Dec 5, 2025

📌 Commit e6b6de4 has been approved by BoxyUwU

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 5, 2025
@bors
Copy link
Collaborator

bors commented Dec 5, 2025

⌛ Testing commit e6b6de4 with merge 1aa9bab...

@bors
Copy link
Collaborator

bors commented Dec 5, 2025

☀️ Test successful - checks-actions
Approved by: BoxyUwU
Pushing 1aa9bab to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Dec 5, 2025
@bors bors merged commit 1aa9bab into rust-lang:main Dec 5, 2025
12 checks passed
@rustbot rustbot added this to the 1.94.0 milestone Dec 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 66428d9 (parent) -> 1aa9bab (this PR)

Test differences

Show 3 test diffs

Stage 2

  • [run-make] tests/run-make/compressed-debuginfo-zstd: pass -> ignore (ignored if LLVM wasn't build with zstd for ELF section compression or LLVM is not the default codegen backend) (J0)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 1aa9bab4ecbce4859eaad53000f78158ebe2be2c --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. pr-check-1: 1945.1s -> 4061.1s (+108.8%)
  2. x86_64-rust-for-linux: 3042.2s -> 5565.7s (+82.9%)
  3. pr-check-2: 2580.7s -> 4645.2s (+80.0%)
  4. x86_64-gnu-gcc: 3413.6s -> 5874.0s (+72.1%)
  5. x86_64-gnu-tools: 3596.7s -> 6014.1s (+67.2%)
  6. x86_64-gnu-miri: 4728.5s -> 7293.4s (+54.2%)
  7. armhf-gnu: 5384.7s -> 7870.1s (+46.2%)
  8. x86_64-gnu-aux: 7096.0s -> 9985.6s (+40.7%)
  9. x86_64-gnu: 7066.6s -> 9532.9s (+34.9%)
  10. x86_64-gnu-nopt: 7614.2s -> 10138.9s (+33.2%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (1aa9bab): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 470.249s -> 470.104s (-0.03%)
Artifact size: 386.85 MiB -> 386.88 MiB (0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-release Relevant to the release subteam, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants